Zeynal Mardanli: Implemented optimized matrix multiplication#5
Open
Lshiroc wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Optimizations:
Blocked matmul: Split matrices into 32×32 tiles so data stays in cache instead of being re-fetched from RAM on every access. Also reordered the inner loops (i-k-j) so memory reads are sequential.
Parallel matmul: Added #pragma omp parallel for over the row loop. Each row of C is independent, so no race conditions. Rows are split evenly across threads with schedule(static).
Challenges:
Test matrices are small (under 300×300), so they already fit in cache which made the blocked version show little to no speedup on most cases.
For very small matrices (e.g. 32×128×32), OpenMP thread startup overhead was larger than the actual computation, giving speedup below 1×.
The loop order in the assignment pseudocode (i-j-k) causes strided memory access inside a block, so I switched to i-k-j to fix that.